Thank you very much for your help.

Thanks for contribution. local test ok. 👍👍

Not relevant to this PR, but I found that Prometheus Collector is not working, it always adds a prefix _ to app when saving data but not in queries.

I found it is other storage common bug due victoriaMetrics adaptation, we will fix it later.

Btw, may i ask how is the protocol compatibility of greptime's prometheus api? We want to try greptime prometheus api in the future, just like victoriaMetrics as a recommond storage. Because we are designing new data stru and integrating the grafana page capabilities, . thanks.

Thanks for contribution. local test ok. 👍👍

Not relevant to this PR, but I found that Prometheus Collector is not working, it always adds a prefix _ to app when saving data but not in queries.

I found it is other storage common bug due victoriaMetrics adaptation, we will fix it later.

Btw, may i ask how is the protocol compatibility of greptime's prometheus api? We want to try greptime prometheus api in the future, just like victoriaMetrics as a recommond storage. Because we are designing new data stru and integrating the grafana page capabilities, . thanks.

Sure, GreptimeDB totally supports Prometheus remote storage(and compatible with vmagent) protocols, please read the doc

https://docs.greptime.com/user-guide/write-data/prometheus#a-note-for-victoriametrics-remote-write

And if you want to use PromQL query API, it's supported too

https://docs.greptime.com/user-guide/query-data/promql#greptimedb-s-http-api